Public/private indicator based access point connection permission

ABSTRACT

Determining a permission for a user equipment to connect to an access point based on the public/private status of the access point device is disclosed. The permission can be based on a historic user equipment density for an area comprising the location of the access point device. The permission can be further based on analysis of an access point device identifier. Analysis of the access point device identifier can be based on comparing a portion of the access point device identifier to a term associated with either a public status or a private status of the access point device. In an embodiment, the access point device identifier can be an SSID, such as for a Wi-Fi network, whereby the SSID can be parsed into keywords that can be compared to the term. Ranking and/or white/blacklisting can be performed based on the analysis of the access point device identifier.

TECHNICAL FIELD

The disclosed subject matter relates to a determining permission relatedto allowing a user equipment to connect with an access point based on anindicator of the access point being a public or private resource.

BACKGROUND

By way of brief background, access points conventionally employ passwordbased access permission. As such, in conventional systems, privatelyowned access points can be accessed by user equipment that has a correctpassword. Moreover, in conventional systems, where the private accesspoint does not have a password enabled, nearly any user equipment canconnect to the access point. These conventional systems can result inuser equipment employing privately owned access points, which can resultin a connected user equipment consuming resources via the access pointthat are not intended for public consumption. Moreover, in some regions,use of a resource via a privately owned access point, or in some cases,even connecting to a privately owned access point, without permission,can be illegal. As an example, where a user equipment is in aresidential neighborhood, it can be illegal for the user equipment toconnect to an open access point, e.g., an access point that does nothave a password set to restrict access, where the access point isprivately owned and permission has not been affirmatively granted forthe user equipment to connect to the private access point. Moreover, apublic access point, e.g., an access point intended to be available forpublic use, cannot easily be discerned from a private access point, moreespecially an open private access point, with conventional techniques.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of an example system that facilitatesdetermining a permission related to an indicator of a public/privateaccess point status in accordance with aspects of the subjectdisclosure.

FIG. 2 is a depiction of an example system that facilitates determininga permission related to an indicator of a public/private access pointstatus based on a keyword and geospatial information in accordance withaspects of the subject disclosure.

FIG. 3 illustrates an example system that facilitates determining apermission related to an indicator of a public/private access pointstatus based on an updateable keyword and supplementary informationrelated to geospatial information in accordance with aspects of thesubject disclosure.

FIG. 4 illustrates an example system that facilitates determining apermission related to an indicator of a public/private access pointstatus based on map information and user equipment location informationin accordance with aspects of the subject disclosure.

FIG. 5 illustrates an example system facilitating determining apermission related to an indicator of a public/private access pointstatus based on stored permission information in accordance with aspectsof the subject disclosure.

FIG. 6 illustrates an example method facilitating determining apermission related to an indicator of a public/private access pointstatus in accordance with aspects of the subject disclosure.

FIG. 7 depicts an example method facilitating receiving by a userequipment, in response to a query from the user equipment, a permissionrelated to an indicator of a public/private access point status inaccordance with aspects of the subject disclosure.

FIG. 8 illustrates an example method facilitating determining apermission related to an indicator of a public/private access pointstatus based on a keyword and map data in accordance with aspects of thesubject disclosure.

FIG. 9 depicts an example schematic block diagram of a computingenvironment with which the disclosed subject matter can interact.

FIG. 10 illustrates an example block diagram of a computing systemoperable to execute the disclosed systems and methods in accordance withan embodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

Conventional access points (APs) typically employ password-basedpermissions to enable a user equipment (UE) to connect to the AP. Assuch, in conventional systems, privately owned APs, e.g., those owned bya private entity and intended solely for use by devices with permissionform the private entity, can be accessed by user equipment that has acorrect password or some other permission indicator. Where the privateaccess point does not have a password enabled, nearly any user equipmentcan connect to the access point, including those without permission fromthe private entity. This can result in user equipment publicallyemploying privately owned access points, which can result in a connecteduser equipment consuming resources via the private access point, e.g.,public consumption without permission from the private entity. Moreover,in some regions, use of a resource via a privately owned AP, or in somecases, even connecting to a privately owned AP, without permission canbe illegal. As an example, where a user equipment is in a residentialneighborhood, it can be illegal for the user equipment to connect to anopen AP, e.g., an AP that does not have a password set to restrictaccess, where the AP is actually a privately owned AP and permission hasnot been affirmatively granted for the user equipment to connect to theprivate AP. Moreover, a public AP, e.g., an access point intended to beavailable for public use, cannot easily be discerned from a private AP,more especially an open private AP, with conventional techniques.Determining a public/private status of an AP can be important to avoidunintended, and possibly illegal, connection to a private AP or accessto a network resource via a private AP.

Observation of human behavior can suggest trends or patterns associatedwith deployment of public/private APs. In an aspect, a public AP, e.g.,an access point intended for public use, can often be located proximateto a business, e.g., a coffee shop can provide an open public AP at thecoffee shop for customer use or to draw in potential customers. Asanother counter example, if would be surprising to find a coffee shop APlocated in a purely residential neighborhood distant from the coffeeshop. As such, the geospatial information associated with an AP can besuggestive of the public/private status of the AP. This observation doesnot preclude the possibility that the coffee shop AP can be a privateAP, e.g., the coffee shop AP can be intended for use only by customersof the coffee shop and not passersby that are not customers, the coffeeshop AP can be for employee use only and not intended for customer useor other public use, etc. As such, other indicia suggestive of apublic/private status of an AP can be important considerations.

In another aspect, user behavior can suggest that many public APsbroadcast custom identifiers, e.g., a renamed service set identifier(SSID), etc. As an example, an AT&T store can provide a public AP thatbroadcasts an SSID of “AT&T OPEN WI-FI” rather than a generic defaultSSID set by the AP device manufacturer. As such, in an aspect, thedisclosed subject matter can analyze AP identifiers to suggest a publicor private AP character. Moreover, analysis of SSID naming by users canbe performed to determine naming trends associated with a public/privateAP status. Naming trends can be employed in generating a “white list”and/or “black list” related to a public/private AP status. In anotheraspect, the naming trends can be employed in ranking or inferring an APstatus, with or without the use of white/black lists. As an example, ablack list can comprise the term “private” such that any SSID includingthe term “private” is excluded from further consideration as a publicAP, e.g., the SSID “AT&T OPEN WI-FI” could be considered public becauseit does not include the word “private” while the SSID “AT&T PRIVATEWI-FI” can be excluded as a public AP based on a blacklist including theword “private. White listing can operate similarly to the inclusion ofan AP into an associated status. For example, where the term “open” ison a whitelist for public status, the SSID “AT&T OPEN WI-FI” can bedetermined to be a public AP based directly on the term “open” in theSSID and the white list. Furthermore, the terms can be employed inranking APs, e.g., the term “personal” can decrease an AP rank in regardto public status, while term “free” can increase the rank of the AP,such that, for example, the SSID “FREE WI-FI” can be more highly rankedas a public AP than an AP broadcasting SSID “John's personal AP”.

In some embodiments, both ranking and white/blacklisting can beperformed. As an example, the SSID “MY PRIVATE FREE WI-FI” can bedetermined to have a private AP status based on the term “private” beingincluded, e.g., the white/blacklist aspect can be controlling, but theSSID can also be ranked as more likely to be public than another SSID of“PRIVATE PERSONAL WI-FI,” which incidentally by inclusion of the term“private” can also be determined to have a private AP status based onwhite/blacklisting. In environments with multiple SSIDs, the combinationof ranking and white/blacklisting can provide a determined order of APsby public/private status. As an example, where the SSIDs are “open AP,free private AP, open free AP, and default SSID,” the ranking can be,from most to least public character, “open free AP, open AP, defaultSSID, free private AP.” This ordering can be based on “open free AP”comprising two terms that indicate public status, “open AP” having oneterm associated with public status, “free private AP” having a net zeropublic/private character (one private term and one public term), and“default SSID” having one term associated with private status. Moreover,the term “free” in the example can be used to classify public APs andthe term “private” can be used to classify private APs, such that frommost public to most private, the example order can be:

Status relative to being Public AP SSID Public (due to use of “free” inSSID) open free AP +1 open AP −1 default SSID NOT Public (due to use of“private” in SSID) free private AP

In an aspect, the geospatial and AP identifier information can beemployed in inferring or determining a status or ranked status of an AP.In an embodiment, rules can be applied to aid in discerning betweenpublic/private character. In some embodiments, rules can imposeweighting in ranking or classifying APs. As an example, geospatial data,can included a location of an AP that is correlated with a known publicretail store, this can be weighted more heavily than the AP SSID beingnamed ‘default SSID’ and, as such, the AP can be determined to be publicin character or can be ranked more highly in public character thanprivate character. Moreover, in some embodiments historical UE density,e.g., a count of devices in an area for a determined period, can be atype of geospatial information. As such, historical UE density can beassociated with a likelihood or probability that proximate APs are of apublic/private status. As an example, a shopping mall can have severalAPs and a historically higher UE density than a residential neighborhooda few blocks away that also has several APs. The higher density of UEsin the region of the shopping mall can be employed to infer or determinethat APs in the region of the shopping mall are more likely, or simplyare, public in character, while the lower historical UE density in theresidential area can be employed to suggest that APs in the residentialarea are private in character. Moreover, the historical UE density canbe employed as a factor in determining public/private character, e.g.,historical UE density, map data, supplementary data associated with amap/location, AP identifier, etc., can be combined in any combination todetermine and/or infer a public/private AP status. As an example, thelocation of an AP in a historically UE dense area can be combined withsupplementary information indicating that a restaurant occupies the samelocation as the AP, which can be combined with the SSID of the AP, todetermine that the AP is likely a public AP. In this example, where SSIDblacklisting is employed and the SSID includes, for example, the term“private,” the AP can be indicated as having a private status despiteother factors indicating that it is likely public.

In an aspect, the AP identifier analysis can be updated based onanalysis of naming conventions in relation to public/private AP status.As such, the disclosed subject matter provides for a learning modewhere, for example, real AP identifiers can be supplied and inferencescan be trained to reflect real public/private AP status associated withthe AP identifiers. In another aspect, analysis of naming conventionscan generate terms that indicate public/private statuses, e.g., auniversity study can provide a list of terms often associated withpublic or private APs, which terms can be employed by the disclosedsubject matter in white/blacklisting, ranking, etc.

In an aspect, map information/data, e.g., geospatial information, can beenriched with supplemental information, e.g., web searches, publicrecords, etc. As an example, a location of an AP, e.g., determined fromthe AP itself, from a UE proximate to the AP, from a network providermap of the AP, etc., can be used to receive supplemental information,such as a web search of the latitude/longitude, address, etc.,indicating that the location is associated with a museum, restaurant,shopping mall, grocery, coffee shop, fast food, municipal building,etc., which can be associated with a particular public/privatecharacter, or the location can be employed to access public recordsindicating a private party sale (residence), zoning information, etc.,that can be associated with another public/private character. Thissupplemental information can, as disclosed herein, be employed indetermining or inferring an AP status and/or a permission for a UE toaccess the AP.

To the accomplishment of the foregoing and related ends, the disclosedsubject matter, then, comprises one or more of the features hereinaftermore fully described. The following description and the annexed drawingsset forth in detail certain illustrative aspects of the subject matter.However, these aspects are indicative of but a few of the various waysin which the principles of the subject matter can be employed. Otheraspects, advantages, and novel features of the disclosed subject matterwill become apparent from the following detailed description whenconsidered in conjunction with the provided drawings.

FIG. 1 is an illustration of a system 100, which facilitates determininga permission related to an indicator of a public/private access pointstatus in accordance with aspects of the subject disclosure. System 100can include access point (AP) permission component (APPC) 110. APPC 110can receive information and can determine a permission related to accessto an AP. APPC 110 can enable access to the permission in the form of APaccess permission data 190. AP access permission data 190 can beemployed, for example, by a user equipment (UE) to enable/disable accessto an AP to reduce a likelihood of accessing a non-public AP withoutpermission.

APPC 110 can receive AP identifier (APID) 120. APID 120 can, in someembodiments be an SSID for a Wi-Fi network. In some embodiments, APID120 can comprise other identification information for an AP connection,e.g., a Bluetooth connection, etc. In an aspect, an SSID can be adefault SSID, e.g., as set by the AP manufacturer, or can be a userselected SSID, e.g., a customized SSID value. The SSID can be employedin determining a public/private character of the associated APconnection. In an aspect, the SSID can be parsed to determine keywordscomprising the SSID value, for example, an SSID of “ABC company publichotspot” can be parsed to capture keywords such as “public,” which canthen be used to infer or determine a public/private character of theassociated SSID connection. Determining the public/private character ofthe AP connection can comprise whitelist, blacklist, ranking, etc.Continuing the previous example, the use of “public” in the SSID canrank the AP connection as more likely public, can be classified aspublic based on a whitelist of public AP terms, can be classified aspublic based on a blacklist of private AP terms, etc. In a furtheraspect, white/blacklisting can be combined with ranking, e.g., APs canbe ranked and certain terms can be used to move an AP to the top orbottom of a ranking, e.g., certain terms can affect rank moresubstantially than other terms, certain terms can be used to fullyescalate, or de-escalate, a rank of an AP, etc. As an example, rankingsof APs from 1 to 5, where 1 indicates public, 3 indicates undetermined,and 5 indicates private, can rank “ABC company public hotspot” as a 1based on inclusion of the term “public,” while the SSID “ABC companyhotspot” can be ranked as 2 for being a non-default name but notincluding the term “public,” e.g., the ranked can be incremented from 3to 2 based on the use of a non-default SSID name. In an aspect, thekeywords used by APPC 110 can be updated to reflect relevant APidentification trends.

APPC 110 can further receive AP location data (APLD) 122. APLD 122 canreflect a location of an AP. In an aspect, AP location information canbe associated with a location of a UE. As an example, a UE can provideAPLD 122 by sending the UE location data, which can be treated as the APlocation. In another aspect, AP location can be known, e.g., defined bya user, mapped by a network provider, the AP can self-locate, e.g., theAP can comprise a GPS, etc., and communicated as APLD 122 to APPC 110.As an example, APID 120 can identify an AP that has previously had alocation reported, e.g., APLD 122, to APPC 110, such that APPC 110 canlook up the previously reported AP location based on the currentlyreceived APID 120.

In some embodiments, APLD 122 can be employed in determiningsupplemental information about the associated AP. As an example, an APcan be associated with APLD 122 indicating an address, such that theaddress can be used to look up business licenses. Where a businesslicense is associated with the lookup address, this can affectdeterminations of, or inference relating to, a public/private status ofthe AP.

In some embodiments, APLD 122 can be employed in determining a locationof an AP with regard to historical UE densities in an area, e.g., acount of UEs in the area for a given period. A historical density of UEscan be associated with a public/private character of an AP. As anexample, a popular restaurant can be associated with a higher count ofUEs in the area of the restaurant for a given evening that can beassociated with a private residence for the same period. Based on thisassociation, higher historical UE densities can be more likely to beproximate to public-type APs. In an aspect, a ‘heat map’ analysis can beoverlaid with a map of a region to illustrate areas of higher historicalUE density, which can, in some embodiments, be associated with anincreased likelihood that APs in ‘hot’ areas are public, while APs in‘cool’ areas are private.

Accordingly, APPC 110 can receive historical UE density information 130.In an aspect, APPC 110 can employ historical UE density information 130in combination with APLD 122 to determine or infer a public/private APstatus. In some embodiments, this can be combined with APID 120 keywordanalysis. As such, APPC 110 can generate AP access permission data 190based on historical UE density information 130, APLD 122 and APID 120.AP access permission data 190 can comprise an inference related to apublic/private AP status, a ranking of APs based on a likelihood ofpublic/private AP status, etc. AP access permission data 190 can beemployed by other devices to determine if a connection to an AP shouldbe initiated based on the public/private AP status. This can aid inreducing a likelihood of a device initiating a connection to a privateAP without permission.

FIG. 2 is a depiction of a system 200 that can facilitate determining apermission related to an indicator of a public/private access pointstatus based on a keyword and geospatial information in accordance withaspects of the subject disclosure. System 200 can include APPC 210. APPC210 can receive information and can determine a permission related toaccess to an AP. APPC 210 can enable access to the permission in theform of AP access permission data 290. AP access permission data 290 canbe employed, for example, by a UE to enable/disable access to an AP toreduce a likelihood of accessing a non-public AP without permission.

APPC 210 can receive APID 220. APID 220 can, in some embodiments be anSSID for a Wi-Fi network. In some embodiments, APID 220 can compriseother identification information for an AP connection, e.g., a Bluetoothconnection, etc. In an aspect, an SSID can be a default SSID, e.g., asset by the AP manufacturer, or can be a user selected SSID, e.g., acustomized SSID value. The SSID can be employed in determining apublic/private character of the associated AP connection. In an aspect,the SSID can be parsed to determine keywords comprising the SSID value,which can then be used to infer or determine a public/private characterof the associated SSID connection.

APPC 210 can comprise keyword component 212. Keyword component 212 canenable keyword analysis of APID 220. In an aspect, keyword component 212can comprise a list of terms. The list of terms can be updateable. Thelist of terms can be compared to keywords parsed from APID 220 to aid indetermining the public/private character of the AP connection, e.g.,whitelisting, blacklisting, ranking, etc. In an aspect keyword component212 can enable comparison of keywords against a list of terms. In afurther aspect, keyword component 212 can enable truncation and/oradaptation of terms or parsed elements of APID 220, e.g., enablingcomparisons with root words, wildcards, etc. As an example, the SSID“MyPrivAP” can be parsed in to “my” “priv” and “AP”, wherein “priv” canbe determined to be a truncated form of the term “private” such that theAP can be determined to more likely private in character based on thisfactor. As another example, the SSID “PRIVATISH” can be treated as theterm ‘privat?? . . . ?’ where the “?” represents wildcard values, suchthat “PRIVATISH” can be interpreted as comprising the term ‘private’ andthe character of the AP can be subsequently determined or inferredaccordingly. In an aspect, white/blacklisting can be combined withranking, e.g., APs can be ranked and certain terms can be used to movean AP to the top or bottom of a ranking. In an aspect, the keywords usedby APPC 210 can be updated to reflect relevant AP identification trends.

APPC 210 can further comprise geospatial correlation component 214.Geospatial correlation component 214 can correlate geospatialinformation related to an AP. In an aspect, geospatial correlationcomponent 214 can receive a map or map data, e.g., map data 240, etc.,receive AP location information, e.g., APLD 222, etc., receivesupplemental map data, etc. Geospatial correlation component 214 cancorrelate the received information to facilitate determining orinferring public/private AP status. As an example, geospatialcorrelation component 214 can receive APID 220, which geospatialcorrelation component 214 can employ to access a previously indicatedlocation of the associated AP, and can then determine a public/privatecharacter based on historical UE density for the previously indicatedlocation associated with the AP. Expanding the example, thepublic/private character of the AP can be further based on map data 240,supplemental map data, APLD 222, etc.

APPC 210 can receive APLD 222. APLD 222 can reflect a location of an AP.In an aspect, AP location information can be associated with a locationof a UE. In another aspect, AP location can be known and communicated asAPLD 222 to APPC 210. In some embodiments, APLD 222 can be employed indetermining supplemental information about the associated AP. In someembodiments, APLD 222 can be employed in determining a location of an APwith regard to historical UE densities in an area, e.g., a count of UEsin the area for a given period. A historical density of UEs can beassociated with a public/private character of an AP. In an aspect, a‘heat map’ analysis can be overlaid with a map of a region to illustrateareas of higher historical UE density, which can, in some embodiments,be associated with an increased likelihood that APs in ‘hot’ areas arepublic, while APs in ‘cool’ areas are private.

Map data 240 can be received by APPC 210. Map data 240 can comprisenearly any type of map information, for example, traffic map data,geographic map data, population density data, land use zoning data,roadway data, etc. Map data can be combined with APLD 222 to provideadditional insight into the public/private nature of an AP. As anexample, APLD 222 can indicate a first location, the first location canbe identified in a commercially zoned region based on land use zoningdata from map data 240, such that APs at the first location can beinferred to be more likely associated with a commercial business than aprivate residence. This factor can then be combined with other factorsin inferring or determining a public/private AP status. Continuing theexample, where the APID 220 for an AP in the commercial district has anSSID “NON_PUBLIC AP,” this AP can be determined to be private despitebeing in the commercial zone, while in contrast, an SSID “default_SSID”can be inferred to more likely be a public AP based on the default nameand the location in the commercial zone.

Further, APPC 210 can receive historical UE density information 230. Inan aspect, APPC 210 can employ historical UE density information 230 incombination with APLD 222 to determine or infer a public/private APstatus. In some embodiments, this can be combined with APID 220 keywordanalysis and/or map data 240. As such, APPC 210 can generate AP accesspermission data 290 based on historical UE density information 230, mapdata 240, APLD 222 and/or APID 220. AP access permission data 290 cancomprise an inference related to a public/private AP status, a rankingof APs based on a likelihood of public/private AP status, etc. AP accesspermission data 290 can be employed by other devices to determine if aconnection to an AP should be initiated based on the public/private APstatus. This can aid in reducing a likelihood of a device initiating aconnection to a private AP without permission.

FIG. 3 illustrates a system 300 that facilitates determining apermission related to an indicator of a public/private access pointstatus based on an updateable keyword and supplementary informationrelated to geospatial information in accordance with aspects of thesubject disclosure. System 300 can comprise include APPC 310. APPC 310can receive information and can determine a permission related to accessto an AP. APPC 310 can enable access to the permission in the form of APaccess permission data 390. AP access permission data 390 can beemployed, for example, by a UE to enable/disable access to an AP toreduce a likelihood of accessing a non-public AP without permission.

APPC 310 can comprise keyword component 312. Keyword component 312 canenable keyword analysis of APID 320. APPC 310 can receive APID 320 atkeyword component 312. APID 320 can, in some embodiments be an SSID fora Wi-Fi network. In some embodiments, APID 320 can comprise otheridentification information for an AP connection. In an aspect, an SSIDcan be a default SSID or can be a user selected SSID. The SSID can beemployed in determining a public/private character of the associated APconnection.

In an aspect, the SSID can be parsed, e.g., via keyword component 312,to determine keywords comprising the SSID value, which can then be usedto infer or determine a public/private character of the associated SSIDconnection. In an aspect, keyword component 312 can comprise a list ofterms. The list of terms can be updateable. The list of terms can becompared to keywords parsed from APID 320 to aid in determining thepublic/private character of the AP connection, e.g., whitelisting,blacklisting, ranking, etc. In an aspect, keyword component 312 canenable comparison of keywords against a list of terms. In a furtheraspect, keyword component 312 can enable truncation and/or adaptation ofterms or parsed elements of APID 320. In an aspect, white/blacklistingcan be combined with ranking, e.g., APs can be ranked and certain termscan be used to move an AP to the top or bottom of a ranking.

In an aspect, the keywords used by APPC 310 can be updated to reflectrelevant AP identification trends. Keywords can be stored in APPC 310via keyword storage component 312. Keyword storage component 312 can beupdated via keyword update 350. In an aspect, the analysis of keywordscan be updated based on analysis of naming conventions in relation topublic/private AP status. As such, APPC 310 can employ a learning modewhere, for example, real AP identifiers can be supplied and inferencescan be trained to reflect real public/private AP status associated withthe AP identifiers. In another aspect, analysis of naming conventionscan generate terms that suggest or indicate public/private AP status,e.g., a list of terms often associated with public or private APs, whichterms can be stored in keyword storage component 312 so that they can beemployed by keyword component 312 in white/blacklisting, ranking, etc.parsed terms from APID 320.

APPC 310 can further comprise geospatial correlation component 314.Geospatial correlation component 314 can correlate geospatialinformation related to an AP. In an aspect, geospatial correlationcomponent 314 can receive a map or map data, e.g., map data 340, etc.,receive AP location information, e.g., APLD 322, etc., receivesupplemental map data, etc. Geospatial correlation component 314 cancorrelate the received information to facilitate determining orinferring public/private AP status. As an example, geospatialcorrelation component 314 can receive APID 320, which geospatialcorrelation component 314 can employ to access a previously indicatedlocation of the associated AP, and can then determine a public/privatecharacter based on historical UE density for the previously indicatedlocation associated with the AP. Expanding the example, thepublic/private character of the AP can be further based on map data 340,supplemental map data, APLD 322, etc.

APPC 310 can receive, at geospatial correlation component 314, APLD 322.APLD 322 can reflect a location of an AP. In an aspect, AP locationinformation can be associated with a location of a UE. In anotheraspect, AP location can be known and communicated as APLD 322 to APPC310. In some embodiments, APLD 322 can be employed in determiningsupplemental information about the associated AP. In some embodiments,APLD 322 can be employed in determining a location of an AP with regardto historical UE densities in an area, e.g., a count of UEs in the areafor a given period. A historical density of UEs can be associated with apublic/private character of an AP. In an aspect, a ‘heat map’ analysiscan be overlaid with a map of a region to illustrate areas of higherhistorical UE density, which can, in some embodiments, be associatedwith an increased likelihood that APs in ‘hot’ areas are public, whileAPs in ‘cool’ areas are private.

Map data 340 can be received by geospatial correlation component 314 viaAPPC 310. Map data 340 can comprise nearly any type of map information,for example, traffic map data, geographic map data, population densitydata, land use zoning data, roadway data, etc. Map data can be combinedwith APLD 322 to provide additional insight into the public/privatenature of an AP via supplemental information capture component 315. Asan example, APLD 322 can indicate a first location, the first locationcan be identified in a commercially zoned region based on land usezoning data from map data 340, and subsequently identified as located ata clothing store in the commercial zone by looking up the address on theinternet via supplemental information capture component 315, such thatAPs at the first location can be inferred to more likely be associatedwith the clothing store than a private residence that might be locatedin the same area of the commercial zone. This factor can then becombined with other factors in inferring or determining a public/privateAP status. Continuing the example, where the APID 320 for an AP of theclothing store has an SSID “Employee Only AP,” this AP can be determinedto be private despite being located in the clothing store, while incontrast, an SSID “default_SSID” can be inferred to more likely be apublic AP based on the default name and the location in the clothingstore. Supplemental information capture component 315 can be instructedto gather supplemental data relating to APLD 322, map data 340,historical UE density information 330, etc., from nearly any public orprivate source. As an example, supplemental information capturecomponent 315 can access 3^(rd) party paid database(s), governmentalland tax data, utility company data, aerial photographs, etc., to gathersupplemental information. In some embodiments, not illustrated,supplemental information capture component 315 can further employ APID320 to gather supplemental information, for example, a registry of APsthat is updated by AP users with public/private AP statuses.

Further, APPC 310 can receive, at geospatial correlation component 314,historical UE density information 330. In an aspect, APPC 310 can employhistorical UE density information 330 in combination with APLD 322 todetermine or infer a public/private AP status. In some embodiments, thiscan be combined with APID 320 keyword analysis and/or map data 340. Assuch, APPC 310 can generate AP access permission data 390 based onhistorical UE density information 330, map data 340, APLD 322 and/orAPID 320.

APPC 310 can store permission information at permission informationstorage component (PSC) 360. PSC 360 can act as a repository fordetermined permissions, e.g., associated with APID 320. PSC 360 cansource AP access permission data 390, which can comprise an inferencerelated to a public/private AP status, a ranking of APs based on alikelihood of public/private AP status, etc. AP access permission data390 can be employed by other devices to determine if a connection to anAP should be initiated based on the public/private AP status. This canaid in reducing a likelihood of a device initiating a connection to aprivate AP without permission. In an aspect, PSC 360 can furtherfacilitate access to historical, e.g., previously determined, permissioninformation. As such, rather than re-determine a public/private statusfor an AP identified by APID 320, APID 320 can be employed by APPC 310,via PSC 360, to enable access, e.g., as AP access permission data 390,to previously determined AP permission information. APPC 310 candetermine if permission information store in PSC 360 is stale, e.g., outof date, too old, based on faulty information, based on less than allavailable information, etc. Where the permission information on PSC 360related to APID 320 is stale, APPC 310 can determine or infer thepublic/private AP status as disclosed hereinabove. Where the permissioninformation is not stale, APPC 310 can employ the stored permissioninformation at PSC 360 rather than re-determining the permissioninformation. In an aspect, even where data is not stale, aredetermination can be made. As an example, where the data on PSC 360 isnot stale, but APPC 310 is not heavily loaded with queries, APPC 310 canre-determine AP access permission data 390 and update the data stored onPSC 360. As another example, where the data stored on PSC 360 isrecently stale, but APPC 310 is heavily loaded, the stale information,in some instances, can be used as AP access permission data 390. In thisexample, other factors can be considered before using stale data, forexample, a history of the AP associated with APID 320 being of a firstAP status, an expected lead time to re-determine permission information,how stale the stored data is, etc. Continuing the example, where thedata is only slightly stale, the AP character for the last 100determinations has always been of a public type, and the APPC is heavilyloaded, APPC 310 can provide the stale data from PSC 360 as AP accesspermission data 390. One or more stale data rules can be employed todetermine if stale data is used, if non-stale data is used, if APPC 310re-determines AP access permission data 390, etc.

FIG. 4 illustrates a system 400 that facilitates determining apermission related to an indicator of a public/private access pointstatus based on map information and user equipment location informationin accordance with aspects of the subject disclosure. System 400 caninclude APPC 410. APPC 410 can receive information and can determine apermission related to access to an AP. APPC 410 can enable access to thepermission in the form of AP access permission data 490. AP accesspermission data 490 can be employed, for example, by UE 470 toenable/disable access to an AP, e.g., AP 402, 404, etc., to reduce alikelihood of accessing a non-public AP without permission. In anaspect, APPC 410 can be located remotely from UE 470 and/or AP 402, 404,etc. APPC 410 can be communicatively coupled to UE 470 viacommunications framework 490, e.g., a network comprising a wired and/orwireless link.

APPC 410 can receive map data 440, e.g., representing the aerial imagein FIG. 4. APPC 410 can further receive APID and APLD, e.g., 422 and424, related to AP 402 and 404 respectively, via UE 470. APID of 422,424, etc., can, in some embodiments be an SSID for a Wi-Fi network. Insome embodiments, APID of 422, 424, etc., can comprise otheridentification information for an AP connection, e.g., a Bluetoothconnection, etc. In an aspect, an SSID can be a default SSID, e.g., asset by the AP manufacturer, or can be a user selected SSID, e.g., acustomized SSID value. The SSID can be employed in determining apublic/private character of the associated AP connection. In an aspect,the SSID can be parsed to determine keywords comprising the SSID value,which can then be used to infer or determine a public/private characterof the associated SSID connection. APLD of 422, 424, etc., can reflect alocation of an AP. In an aspect, AP location can be known andcommunicated as APLD of 422, 424, etc., to APPC 410. In someembodiments, APLD of 422, 424, etc., can be employed in determiningsupplemental information about the associated AP. In some embodiments,APLD of 422, 424, etc., can be employed in determining a location of anAP with regard to historical UE densities in an area, e.g., a count ofUEs in the area for a given period.

In an embodiment, an AP location can be based on a location of a UE.Where a UE is proximate to an AP, e.g., sufficiently close to be in theservice area of the AP, the location of the UE can be consideredaccurate enough to also represent the location of the AP. As such, UElocation data 472 can be substituted from APLD of 422, 424, etc., insome circumstances, e.g., where the location of the AP is otherwise notknown, etc. As illustrated in FIG. 4, where UE 470 is located proximateto and between AP 402 an AP 404, the UE location can be used as the APlocation. It will be noted however, that the actual locations of theAPs, e.g., 402 and 404, are not the same as the UE location and canresult in different permission results. For example, where AP 402employs accurate APLD information, it can be determined to be in theresidential area, while if AP 402 uses UE 470 location as the locationof AP 402, it will indicate that UE 402 is located in the business area.This can contrast with AP 404, which will show as being located in thebusiness area for both an accurate location of AP 404 as well as whensubstituting the UE location for the location of AP 404. As such, basedon location substitution rules, a UE location can be substituted incertain conditions, e.g., where a location for an AP is not otherwiseavailable, where a location of a UE is determined to be better than anotherwise available location of an AP, etc. As an example, where a UEuses a radio access technology known to have a small coverage area, suchas near field communication, etc., a location substitution rule canindicate that it is acceptable to substitute the UE location where it isexpected to be more accurate than an otherwise available location forthe AP.

FIG. 5 illustrates a system 500 that facilitates determining apermission related to an indicator of a public/private access pointstatus based on stored permission information in accordance with aspectsof the subject disclosure. System 500 can comprise APPC 510. APPC 510can receive information and can determine a permission related to accessto an AP, e.g., AP 502. APPC 510 can enable access to the permission inthe form of AP access permission data, e.g., 190, 290, 390, 490, etc. APaccess permission data can be employed, for example, by UE 570 toenable/disable access to AP 502 to reduce a likelihood of accessing anon-public AP without permission.

APPC 510 can comprise PSC 560. PSC 560 can act as a repository fordetermined permissions, e.g., associated with an identified AP, e.g., AP502. PSC 560 can enable access to AP access permission data, which cancomprise an inference related to a public/private AP status, a rankingof APs based on a likelihood of public/private AP status, etc. AP accesspermission data can be employed by other devices, e.g., UE 570, etc., todetermine if a connection to an AP, e.g., AP 502, etc., should beinitiated based on the public/private AP status. This can aid inreducing a likelihood of a device initiating a connection to a privateAP without permission. In an aspect, PSC 560 can further facilitateaccess to historical, e.g., previously determined, permissioninformation. This can reduce instances where a public/private status forAP 502 is re-determined. PSC 560 can enable access to previouslydetermined AP permission information for AP 502. In an aspect, APPC 510can determine if permission information stored in PSC 560 is stale,e.g., out of date, too old, based on faulty information, based on lessthan all available information, etc. Where the permission informationstored on PSC 560 is stale, APPC 510 can determine or infer thepublic/private AP status for AP 502 as disclosed herein. Where thepermission information is not stale, APPC 510 can employ the storedpermission information from PSC 560 rather than re-determining thepermission information. In some embodiments, even where data is notstale, a redetermination can be made. In some embodiments, where thedata is stale, other factors can be considered that can enable use ofthe stale data. As an example, a stable AP state history of AP 502 canbe determined to be sufficient to re-use stale data from PSC 560 ratherthat to re-determine the AP state. One or more stale data rules can beemployed to determine if stale data is to be used, if non-stale data isto be used, if APPC 510 will re-determine AP access permission data forAP 502, etc.

APID can be communicated, vie UE 570 and communication framework 590, toAPPC 510. APID from AP 502 can be parsed into keywords. Keyword analysisof the APID, for example, of an SSID for a Wi-Fi network, can beemployed in determining a public/private character of the associated APconnection. In an aspect, a list of keyword terms used in analysis ofthe APID parse can be updateable. The list of terms can be compared toparsed keywords to aid in determining the public/private character ofthe AP connection, e.g., whitelisting, blacklisting, ranking, etc. In afurther aspect, keywords can be truncated and/or adapted, e.g., rootwords of terms, wildcards, etc. In an aspect, white/blacklisting can becombined with ranking, e.g., APs can be ranked and certain terms can beused to move an AP to the top or bottom of a ranking.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 6-FIG. 8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 6 illustrates a method 600 facilitating determining a permissionrelated to an indicator of a public/private access point status inaccordance with aspects of the subject disclosure. At 610, method 600can comprise receiving an access point identifier (APID) associated withan access point (AP). At 610, method 600 can further comprise receivinghistorical user equipment (UE) density information for a regioncomprising the AP. In some embodiments the APID can be an SSID,Bluetooth ID, etc. The APID can be a default APID, e.g., set by the APmanufacturer, etc., or can be a custom APID, e.g., an APID set by auser, etc., for example a user selected SSID. The APID, or portionsthereof, can be compared to terms that are associated with public APs orprivate APs. As an example, where the term ‘open’ is determined to beused most frequently in APIDs for publicly accessible APs, the term‘open’ when found in an APID can be indicative of the associated APbeing a publicly accessible AP. APID analysis can enable ranking,whitelisting, blacklisting, etc., of APIDs and associated APs.

In an aspect, historical UE density, e.g., a count of UEs in an area fora period, can be correlated to public/private AP states. As an example,it can be less common for high counts of UEs to be in an area that isnot public. While this can occur, for example, a private vacation resortcan be non-public and still be associated with a high UE density, it isgenerally more common for areas like shopping malls, grocery stores,sporting events, etc., that are generally public to be associated withhigh UE densities. Moreover, public areas can correspond to public APresources. As before, public areas can comprise private APs, but oftencan comprise public APs. As such, correlations between historical UEdensity and public AP character can be employed as a factor indetermining a permission related to allowing UE to connect to an AP.

At 620, method 600 can comprise determining a permission correlated tothe APID. The permission can be based on the historical UE density andthe APID, e.g., analysis of the APID for keyword terms. As an example,where the AP is located in a historically dense UE area, this can morecommonly be associated with a public AP character. Similarly, where theAPID comprises a term associated with a public AP character, thecombination of the APID and historical UE density can lead to adetermination or inference that the AP is a public AP and the permissioncan be determined accordingly. As another example, where the AP islocated in a low-density area and the APID comprises terms indicating aprivate AP, e.g., “joe's private Wi-Fi”, etc., the permission can beassociated with a private AP character. Moreover, where the historicalUE density and APID analysis can be factors contributing to ranking ofAPs, the AP can be ranked as more private or more public in comparisonto other APs in the area. Furthermore, certain terms in the APIDanalysis can be employed to designate an AP as private or publicregardless of other factors. As such, where the APID comprises a term,for example, “public library,” even where the AP is located in a low UEdensity area, the permission can correspond to a public AP character.

At 630, access to the permission can occur in method 600. The access canoccur in response to receiving a query comprising the APID. Thepermission can facilitate determining if a UE can connect to the APassociated with the APID. At this point, method 600 can end. As anexample, method 600 can receive a query from a UE, wherein the queryidentified the AP, e.g., the query includes the APID. In response,method 600 can facilitate access to the permission determined at 620.The permission can then be employed, for example, by the UE to determineif the AP is public/private, e.g., if the UE can connect to the APassociated with the APID. Where an AP is private, the permission canfacilitate determining that the UE should not connect to the AP. Incontrast, where the AP is public, the permission can facilitatedetermining that the UE can connect to the AP.

FIG. 7 illustrates a method 700 that facilitates receiving by a userequipment, in response to a query from the user equipment, a permissionrelated to an indicator of a public/private access point status inaccordance with aspects of the subject disclosure. At 710, method 700can comprise generating a query comprising an APID associated with anAP. As an example, a UE can move into a coverage area of an AP and canobserve the APID, e.g., a SSID for a Wi-Fi AP. The example UE can thengenerate a query with the APID to check if the AP is public or private.The query can relate to determining a permission based on historical UEdensity for a region comprising the AP and analysis of the APID itself.The permission can facilitate determining if a UE can connect to the APassociated with the APID.

At 720, method 700 can comprise, in response to receiving a reply to thequery, wherein the response comprises the permission, determining if theUE can connect to the AP associated with the APID based on thepermission. At this point, method 700 can end. The response to the querygenerated at 710 can comprise a permission. The permission can be basedon the APID, or portions thereof, which can be compared to terms thatare associated with public APs or private APs. As an example, where theterm ‘free’ is determined to be used most frequently in APIDs forpublicly accessible APs, the term ‘free’ when found in an APID can beindicative of the associated AP being a publicly accessible AP. APIDanalysis can enable ranking, whitelisting, blacklisting, etc., of APIDsand associated APs. The permission can further be based on historical UEdensity, e.g., a count of UEs in an area for a period, can be correlatedto public/private AP states. As an example, there can be a correlationbetween high counts of UEs and an area being public, e.g., a high UEdensity can be generally more common for areas like shopping malls,grocery stores, sporting events, etc., that are typically public.Moreover, public areas can correspond to public AP resources. As such,correlations between historical UE density and an AP having a publiccharacter can be employed as a factor in determining the permissionrelated to allowing UE to connect to the AP. As an example, where the APis located in a historically dense UE area, this can more commonly beassociated with a public AP character. Similarly, where the APIDcomprises a term associated with a public AP character, the combinationof the APID and historical UE density can lead to a determination orinference that the AP is a public AP and the permission can bedetermined accordingly. As another example, where the AP is located in alow-density area and the APID comprises terms indicating a private AP,the permission can be associated with a private AP character. Moreover,where the historical UE density and APID analysis can be factorscontributing to ranking of APs, the AP can be ranked as more private ormore public in comparison to other APs in the area. Furthermore, certainterms in the APID analysis can be employed to designate an AP as privateor public regardless of other factors.

Method 700, at 720, can comprise, for example, a UE receiving a reply toa query about a nearby access point. The permission can generallyindicate a public or private nature of the APID associated with the AP.As such, the permission can facilitate the UE determining if it canconnect to the AP, e.g., the UE can avoid connecting to private APs andcan pursue connecting to public APs. In an aspect, reporting of APIDsand location information by a first UE can enable determining ofpermissions correlated to the APID. These permissions can then bereturned to the first UE or to other UEs.

FIG. 8 illustrates a method 800 that facilitates determining apermission related to an indicator of a public/private access pointstatus based on a keyword and map data in accordance with aspects of thesubject disclosure. At 810, method 800 can comprise receiving APID andlocation information for an AP. In an aspect, the APID can be parsed todetermine keywords comprising the APID, for example, an SSID for a Wi-FiAP can be parsed to capture keywords, which can then be used to infer ordetermine a public/private character of the associated SSID connection.Determining the public/private character of the AP connection cancomprise whitelist, blacklist, ranking, etc. In a further aspect,white/blacklisting can be combined with ranking, e.g., APs can be rankedand certain terms can be used to move an AP to the top or bottom rank,e.g., certain terms can affect rank more substantially than other terms,certain terms can be used to fully escalate, or de-escalate, a rank ofan AP, etc. In an aspect, the terms used in analysis of keywords parsedfrom an APID can be updated to reflect relevant AP identificationtrends.

At 820, historical UE density information for an area comprising alocation of the AP can be received. The location of the AP can bedetermined by the AP, e.g., where the AP comprises a location technologysuch as GPS, etc., by systems that map the location of the AP, e.g.,deployment information by a network provider, by a user, etc., bysubstituting proximate UE location information, e.g., the UE is near tothe AP and the UE location can be effectively substituted for the APlocation, etc. The historical UE density information for the AP locationcan reflect a probability that the AP is a public or private AP. As anexample, an airport can be associated with public APs and a high densityof UEs in comparison to a sleepy rural residence that can be associatedwith a private AP and very low historical UE density.

At 830, method 800 can comprise determining public and private portionsof the area based on the historical UE density information. In anaspect, portions of the area, e.g., grids, bins, etc., can be allocateda score relating to a level of public or a level of private AP characterbased on the historical UE density for the area. As an example, if agrid pattern of 100 meters by 100 meters is used to define 100 portionsof a 1 km by 1 km area for which historical UE information is receivedand wherein the location of the AP is within the area, then the densityof each grid square can be determined from the historical UE densityinformation. The UE density can then be used to determine a score thatcorresponds to a level of public/private character for the grid squarebased on the historical UE density. A location of an AP, where the AP isin the area, will therefore fall within one of the grid squares and cantherefore be associated with the score that corresponds to the level ofpublic/private character for that grid square.

At 840, The APID can be parsed into keywords and ranked based oncomparing the keywords to a list of determined terms. Analysis of namingconventions in relation to public/private AP status can be employed todetermine a list of terms or an update tot a list of terms. As such,real AP identifiers can be analyzed and inferences or determinations canbe made that reflect real public/private AP status associated with theAP identifiers. This can result in a list of terms often associated withpublic or private APs, which terms can be employed inwhite/blacklisting, ranking, etc.

Method 800, at 850, can comprise adapting the ranking of the APID, from840, based on the location of the AP and the public/private score from830. Where an APID is ranked based on the analysis of keywords in theAPID, the rank can be further adapted based on correlations between thelocation and historical UE density as it relates to public/private APstatus. In an embodiment, although not illustrated, the ranking can befirst based on the historical UE density and then adapted based on theAPID keyword analysis.

At 860, method 800 can comprise enabling access to the ranking of theAPID in response to receiving a query comprising the APID. At this pointmethod 800 can end. In an aspect, the response can enable a UE todetermine if it will initiate a connection to the AP associated with theAPID, e.g., where the ranking indicates a public character, the UE canconnect, in contrast to the ranking indicating a private character wherethe UE would not initiate a connection.

FIG. 9 is a schematic block diagram of a computing environment 900 withwhich the disclosed subject matter can interact. The system 900 includesone or more remote component(s) 910. The remote component(s) 910 can behardware and/or software (e.g., threads, processes, computing devices).In some embodiments, remote component(s) 910 can include servers,personal servers, wireless telecommunication network devices, etc. As anexample, remote component(s) 910 can be UE 470, 570, etc., access point402, 404, 502, etc.

The system 900 also includes one or more local component(s) 920. Thelocal component(s) 920 can be hardware and/or software (e.g., threads,processes, computing devices). In some embodiments, local component(s)920 can include, for example, APPC 110, 210, 310, 410, 510, etc.

One possible communication between a remote component(s) 910 and a localcomponent(s) 920 can be in the form of a data packet adapted to betransmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 910 and a local component(s)920 can be in the form of circuit-switched data adapted to betransmitted between two or more computer processes in radio time slots.The system 900 includes a communication framework 940 that can beemployed to facilitate communications between the remote component(s)910 and the local component(s) 920, and can include an air interface,e.g., Uu interface of a UMTS network. Remote component(s) 910 can beoperably connected to one or more remote data store(s) 950, such as ahard drive, SIM card, device memory, etc., that can be employed to storeinformation on the remote component(s) 910 side of communicationframework 940. Similarly, local component(s) 920 can be operablyconnected to one or more local data store(s) 930, that can be employedto store information on the local component(s) 920 side of communicationframework 940.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can include both volatile and nonvolatile memory,by way of illustration, and not limitation, volatile memory 1020 (seebelow), non-volatile memory 1022 (see below), disk storage 1024 (seebelow), and memory storage 1046 (see below). Further, nonvolatile memorycan be included in read only memory, programmable read only memory,electrically programmable read only memory, electrically erasable readonly memory, or flash memory. Volatile memory can include random accessmemory, which acts as external cache memory. By way of illustration andnot limitation, random access memory is available in many forms such assynchronous random access memory, dynamic random access memory,synchronous dynamic random access memory, double data rate synchronousdynamic random access memory, enhanced synchronous dynamic random accessmemory, Synchlink dynamic random access memory, and direct Rambus randomaccess memory. Additionally, the disclosed memory components of systemsor methods herein are intended to comprise, without being limited tocomprising, these and any other suitable types of memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, including single-processor ormultiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,netbook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, part of APPC 110,210, 310, 410, 510, etc., access point 402, 404, 502, etc., UE 470, 570,etc., includes a processing unit 1014, a system memory 1016, and asystem bus 1018. System bus 1018 couples system components including,but not limited to, system memory 1016 to processing unit 1014.Processing unit 1014 can be any of various available processors. Dualmicroprocessors and other multiprocessor architectures also can beemployed as processing unit 1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 1194), and small computer systems interface.

System memory 1016 can include volatile memory 1020 and nonvolatilememory 1022. A basic input/output system, containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1020 includes read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, Synchlink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1012 can also include removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1024to system bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, read only memory, programmable read only memory,electrically programmable read only memory, electrically erasable readonly memory, flash memory or other memory technology, compact disk readonly memory, digital versatile disk or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or other tangible media which can be used tostore desired information. In this regard, the term “tangible” herein asmay be applied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating intangible signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can includenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium. As such, for example, a computer-readable medium can compriseexecutable instructions stored thereon that, in response to execution,cause a system comprising a processor to perform operations, comprising:receiving APID 120, 220, 320, 422, 424, etc., APLD 122, 222, 322, 422,424, etc., and in response determine a value related to a public/privatecharacter of an AP associated with the APID.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. As an example, a user interface can allow entry ofuser preference information, etc., and can be embodied in a touchsensitive display panel, a mouse input GUI, a command line controlledinterface, etc., allowing a user to interact with computer 1012. As anexample, UI Component 584 can receive touch, motion, audio, visual, orother types of input. Input devices 1036 include, but are not limitedto, a pointing device such as a mouse, trackball, stylus, touch pad,keyboard, microphone, joystick, game pad, satellite dish, scanner, TVtuner card, digital camera, digital video camera, web camera, cellphone, smartphone, tablet computer, etc. These and other input devicesconnect to processing unit 1014 through system bus 1018 by way ofinterface port(s) 1038. Interface port(s) 1038 include, for example, aserial port, a parallel port, a game port, a universal serial bus, aninfrared port, a Bluetooth port, an IP port, or a logical portassociated with a wireless service, etc. Output device(s) 1040 use someof the same type of ports as input device(s) 1036.

Thus, for example, a universal serial busport can be used to provideinput to computer 1012 and to output information from computer 1012 toan output device 1040. Output adapter 1042 is provided to illustratethat there are some output devices 1040 like monitors, speakers, andprinters, among other output devices 1040, which use special adapters.Output adapters 1042 include, by way of illustration and not limitation,video and sound cards that provide means of connection between outputdevice 1040 and system bus 1018. It should be noted that other devicesand/or systems of devices provide both input and output capabilitiessuch as remote computer(s) 1044. As an example, user input can becaptured in relation to terms used to analyzed APID 120, 220, 320, 422,424, etc., map data 240, 340, 440, etc., to enable determining apublic/private status of an AP related to the APID, in accordance withthe presently disclosed subject matter.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, cloud service, a workstation, amicroprocessor based appliance, a peer device, or other common networknode and the like, and typically includes many or all of the elementsdescribed relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies include fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring and the like. Wide areanetwork technologies include, but are not limited to, point-to-pointlinks, circuit-switching networks like integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines. As noted below, wireless technologies may be used inaddition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “eNodeB,” “home Node B,” “home accesspoint,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream to and from a set ofsubscriber stations or provider enabled devices. Data and signalingstreams can include packetized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include broadcasttechnologies (e.g., sub-Hertz, extremely low frequency, very lowfrequency, low frequency, medium frequency, high frequency, very highfrequency, ultra-high frequency, super-high frequency, terahertzbroadcasts, etc.); Ethernet; X.25; powerline-type networking, e.g.,Powerline audio video Ethernet, etc.; femtocell technology; Wi-Fi;worldwide interoperability for microwave access; enhanced general packetradio service; third generation partnership project, long termevolution; third generation partnership project universal mobiletelecommunications system; third generation partnership project 2, ultramobile broadband; high speed packet access; high speed downlink packetaccess; high speed uplink packet access; enhanced data rates for globalsystem for mobile communication evolution radio access network;universal mobile telecommunications system terrestrial radio accessnetwork; or long term evolution advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receivingan access point device identifier associated with an access pointdevice; receiving a historical density of user equipments for an area,wherein the access point device is located in the area, wherein thehistorical density for the area is derived from historical densities forareas comprising the area, and wherein the historical densities arebased on a historical count of different user equipments in the areas isdetermined for a determined time period; determining a status of theaccess point device based on the historical density; and enabling accessto the status for a user equipment to facilitate the user equipmentinitiating a connection to the access point device based on the status.2. The system of claim 1, wherein the access point device is a serviceset identifier.
 3. The system of claim 2, wherein the service setidentifier is a service set identifier for a Wi-Fi network employing anInstitute of Electrical and Electronics Engineers 802.11 protocol. 4.The system of claim 1, wherein the operations further comprise: parsinga keyword from the access point device identifier; and updating thestatus in response to comparing the keyword to a term associated with afirst status.
 5. The system of claim 4, wherein the first statuscorresponds to an increased likelihood that the access point device isintended to be a publically available access point device.
 6. The systemof claim 4, wherein the first status corresponds to a decreasedlikelihood that the access point device is a private access point deviceintended for non-public use.
 7. The system of claim 4, wherein the termis updated in response to an analysis of access point device identifiersin relation to a public/private access point status.
 8. The system ofclaim 1, wherein the area comprises a delineation of a grid pattern ofgrid squares, and wherein a grid square of the grid squares is about 100meters by 100 meters.
 9. The system of claim 1, wherein the historicaldensity represents a historical count of unique user equipments in thearea of the areas for the determined time period.
 10. The system ofclaim 9, wherein the historical density is apportionable into gridsquares of a grid pattern delineation of the area, and wherein a gridsquare of the grid squares is assigned the historical count of uniqueuser equipments for the grid square of the area of the areas for thedetermined time period for a determined granularity of the grid patterndelineation.
 11. The system of claim 1, wherein a first location of theaccess point device is determined by substitution of a second locationof a user equipment determined to be within a service area of the accesspoint device.
 12. The system of claim 1, wherein the operations furthercomprise: receiving map data comprising business location informationrepresentative of locations of business entities, and wherein thedetermining the status of the access point device is further based onthe map data.
 13. A mobile device, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receivingan access point device identifier from an access point device;generating a query related to a character of the access point device,wherein the query comprises the access point identifier, and wherein thecharacter relates to whether the access point device has a publiccharacteristic as opposed to a private characteristic; receiving aresponse to the query, wherein the response comprises a permissionscore, wherein the permission score is based on a historical density ofuser equipments in an area comprising the location of the access pointdevice and an analysis of the access point device identifier, andwherein the historical density of the user equipments in the area isbased on a historical count of different user equipments in the areaduring a determined historical period; and initiating a connection tothe access point device based on the permission score.
 14. The mobiledevice of claim 13, wherein the access point device is a first accesspoint device, and wherein the permission score represents a rank of thefirst access point device relative to a status of a second access pointdevice as to whether the second access point device has the publiccharacteristic or the private characteristic.
 15. The mobile device ofclaim 13, wherein the analysis of the access point device identifiercomprises parsing the access point device identifier into arepresentation comprising a keyword and comparing the keyword of therepresentation to a term of a group of terms, and wherein the group ofterms is associated with the character of the access point device. 16.The mobile device of claim 13, wherein the access point device isdetermined to be within the area based on a location of the mobiledevice.
 17. A method, comprising: determining, by a network devicecomprising a processor, a status of an access point device based on ahistorical density of user equipments for an area and a correlationbetween a portion of an access point device identifier and a determinedterm, wherein the access point device is located in the area, andwherein the historical density of the user equipments for the area isbased on a count of different user equipments in the area during adetermined historical period; and enabling, by the network device,access to the status for a user equipment to facilitate a user equipmentdetermining an availability of the access point device based on thestatus.
 18. The method of claim 17, wherein the status relates towhether the access point device is a non-residential use access pointdevice as opposed to a public use access point device.
 19. The method ofclaim 18, wherein the status relates to whether the access point deviceis a residential use access point device as opposed to a private useaccess point device.
 20. The method of claim 18, wherein the accesspoint device identifier is a service set identifier for a networkemploying a Wi-Fi protocol.